Online data management

ABSTRACT

Technologies are generally described for a data management scheme. In some examples, a method may include displaying, by a client device, a representation of a data item received from a server; transmitting, by the client device, to the server, a request to access the data item and information regarding the request to access, in response to a user input; updating, by the server, the representation of the data item to further include the information regarding the request to access; and displaying, by the client device, the updated representation of the data item received from the server.

BACKGROUND

High-end mobile electronic devices, such as smartphones and tablets,provide ubiquitous network connectivity to the users thereof. Forexample, a user may use his/her mobile electronic devices to read onlinedata such as an electronic mail, a post in an SNS (social networkingservice), or a news article at anytime, anywhere. However, due to therelatively small sizes of the mobile electronic devices, the user mayexperience difficulty with reading the online data. In such cases, theuser may want to read the online data again using other electronicdevices with larger screens.

SUMMARY

In an example, a method may include displaying, by a client device, arepresentation of a data item received from a server; transmitting, bythe client device, to the server, a request to access the data item andinformation regarding the request to access, in response to a userinput; updating, by the server, the representation of the data item tofurther include the information regarding the request to access; anddisplaying, by the client device, the updated representation of the dataitem received from the server.

In another example, a data management server may include a receiver unitconfigured to receive, from a client device, a request to access a dataitem and information regarding the request to access; and arepresentation generation unit configured to generate a representationof the data item to include the received information regarding therequest to access.

In yet another example, a method performed under control of a datamanagement server may include receiving, from a client device, a requestto access a data item; receiving, from the client device, informationregarding the request to access; and generating a representation of thedata item to include the information regarding the request to access.

In still another example, a computer-readable storage medium may storethereon computer-executable instructions that, in response to execution,cause a processor to perform operations, including displaying arepresentation of a data item stored in a data storage; displaying anindication of whether the data item has been accessed by a user account;and displaying information regarding a previous access by the useraccount for the data item.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other features of this disclosure will become moreapparent from the following description and appended claims, taken inconjunction with the accompanying drawings. Understanding that thesedrawings depict only several embodiments in accordance with thedisclosure and arc, therefore, not to be considered limiting of itsscope, the disclosure will be described with additional specificity anddetail through use of the accompanying drawings, in which:

FIG. 1 schematically shows an illustrative example of an environment inwhich a data management server provides client devices with arepresentation of data items, arranged in accordance with at least someembodiments described herein;

FIG. 2 schematically shows an illustrative example of a representationof data items that is displayed on a client device, arranged inaccordance with at least some embodiments described herein;

FIG. 3 shows a schematic block diagram illustrating an examplearchitecture of a data management server for implementing a datamanagement scheme, arranged in accordance with at least some embodimentsdescribed herein;

FIG. 4 shows a schematic block diagram illustrating another examplearchitecture of a data management server for implementing a datamanagement scheme, arranged in accordance with at least some embodimentsdescribed herein;

FIG. 5 shows a schematic block diagram illustrating an examplearchitecture of a data manager for implementing a data managementscheme, arranged in accordance with at least some embodiments describedherein;

FIG. 6 shows an example flow diagram of a process for a data managementserver implementing a data management scheme, arranged in accordancewith at least some embodiments described herein;

FIG. 7 illustrates an example computer program product that may beutilized to implement a data management scheme, arranged in accordancewith at least some embodiments described herein; and

FIG. 8 is a block diagram illustrating an example computing device thatmay be utilized to implement a data management scheme, arranged inaccordance with at least some embodiments described herein.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented herein. It will be readily understood that the aspects of thepresent disclosure, as generally described herein, and illustrated inthe drawings, can be arranged, substituted, combined, separated, anddesigned in a wide variety of different configurations, all of which areexplicitly contemplated herein.

This disclosure is generally drawn, inter alia, to methods, apparatuses,systems, devices, and computer program products related to online datamanagement. Further, technologies are herein generally described forproviding a user, who may use one or more devices by which he/she mayaccess online data, with a scheme to keep track of by which devicehe/she has accessed the online data and/or where he/she has accessed theonline data.

In some examples, the user may try to access a data item (e.g., read anelectronic mail, an SNS (social networking service) post, or a newsarticle), which may be stored in a remote data storage, using a firstdevice. In such cases, the first device may transmit a request to accessthe data item to a data management server in response to a user input,and then a procedure of accessing the data item from the first devicemay be initiated. The data management server may be hosted by or incooperation with a service provider associated with the data item suchas, for example, an electronic mail service provider, an SNS provider,or an online content provider.

In some examples, the first device may also transmit, to the datamanagement server, information regarding the request to access,including device information regarding the first device and/or locationinformation of the first device at the time the request was transmitted.Examples of the device information regarding the first device mayinclude a name of the first device, a type of the first device, a screensize of the first device, a display resolution of the first device,and/or information regarding a network to which the first device iscommunicatively connected. Further, examples of the location informationof the first device at the time the request was transmitted may includeinformation regarding a registered location that is specific to theuser, GPS (Global Positioning System) coordinates of the first device,information regarding a cellular network to which the first device iscommunicatively connected, information regarding a Wi-Fi access point towhich the first device is communicatively connected, an IP address,and/or information regarding communication between the first device andat least one nearby beacon. By way of example, but not limitation, whenthe user tries to read the data item using a smartphone in a subway, thesmartphone may transmit the device information identifying itself and/orthe location information indicating that it is in the subway. By way ofanother example, but not limitation, when the user tries to read thedata item using a personal computer (PC) in an office, the PC maytransmit the device information identifying itself and/or the locationinformation indicating that it is in the office.

Then, in some examples, the data management server may generate arepresentation of the data item to include the information regarding therequest to access. For instance, the representation of the data item mayinclude an indication of whether the data item has been previouslyaccessed by a device owned and/or controlled by the user that may beidentified based on one or more user accounts to which the user hasregistered and/or signed in to, the device information regarding thefirst device that has accessed the data item, and/or the locationinformation regarding a location at which the first device has accessedthe data item. Then, in some examples, the data management server mayprovide the representation of the data item to the first device and/orone or more other devices owned and/or controlled by the user, so thatthe user may be aware by which device he/she accessed the data itemand/or where he/she accessed the data item.

In some further examples, the data management server may receive, fromthe first device and/or a second device owned and/or controlled by theuser, a subsequent request to access the data item. In such cases, thedata management server may also receive information regarding thesubsequent request to access. Then, the data management server mayupdate the representation of the data item to include the informationregarding the subsequent request to access.

FIG. 1 schematically shows an illustrative example of an environment inwhich a data management server provides client devices with arepresentation of data items, arranged in accordance with at least someembodiments described herein.

As depicted, a data management server 100 may be communicatively coupledto client devices 110 a and/or 110 b, which may be owned and/orcontrolled by a user 120, over a network such as, for example, theInternet, a cellular network, a wide area network (WAN), a metropolitanarea network (MAN), a local area network (LAN), a campus area network(CAN), a virtual private network (VPN), etc. Client devices 110 a and/or110 b may be of any type of electronic device configured to store,retrieve, compute, transmit and/or receive data, including, for example,a smartphone, a mobile phone, a personal digital assistant (PDA), atablet, a personal computer such as a laptop computer or a desktopcomputer, a television, a gaming console, etc.

In some embodiments, data management server 100 may be hosted by or incooperation with an online service provider such as, for example, anelectronic mail service provider, an SNS provider, or an online contentprovider, so that user 120 may access the data items (e.g., electronicmails, posts in one or more SNS (social networking service), or newsarticles, etc.) provided by the online service provider based on, atleast in part, interaction between data management server 100 and clientdevices 110 a and/or 110 b owned and/or controlled by user 120.

In some embodiments, data management server 100 may identify anassociation between client devices 110 a and/or 110 b and user 120 basedon one or more user accounts of user 120. That is, data managementserver 100 may determine that client devices 110 a and/or 110 b areowned and/or controlled by user 120 based on the user accounts used byuser 120 to log on to data management server 100 from client devices 110a and/or 110 b.

In some embodiments, user 120 may use client device 110 a (e.g., asmartphone as illustrated in FIG. 1) to try to initially access one ofthe data items (e.g., read an electronic mail, an SNS post, or a newsarticle, etc.), which may be stored in a remote data storage associatedwith the online service provider. In such cases, client device 110 a maytransmit a request to access the data item to data management server100, in response to an input of user 120. Client device 110 a may alsotransmit, to data management server 100, information regarding therequest to access, including device information regarding client device110 a and/or location information of client device 110 a at the time oftransmitting the request. Examples of the device information regardingclient device 110 a may include a name of client device 110 a, a type ofclient device 110 a, a screen size of client device 110 a, a displayresolution of client device 110 a, and/or information regarding anetwork to which client device 110 a is communicatively connected.Further, examples of the location information of client device 110 a atthe time of transmitting the request may include information regarding aregistered location that is specific to user 120, GPS (GlobalPositioning System) coordinates of client device 110 a, informationregarding a cellular network to which client device 110 a iscommunicatively connected, information regarding a Wi-Fi access point towhich client device 110 a is communicatively connected, and/orinformation regarding communication between client device 110 a and atleast one nearby beacon.

In some further embodiments, data management server 100 may generate arepresentation of the data item to include the information regarding therequest to access. Then, data management server 100 may provide therepresentation of the data item to client devices 110 a and/or 110 b, sothat user 120 may be aware by which device he/she accessed the data itemand/or where he/she accessed the data item. Example embodiments of therepresentation of the data item will be described in more detail withreference to FIG. 2.

In some embodiments, when user 120 tries to access the same data itemagain using client device 110 a, client device 110 a may transmit, todata management server 100, a subsequent request to access the dataitem. In such cases, data management server 100 may receive, from clientdevice 110 a, the subsequent request to access, with informationregarding the subsequent request to access including device informationregarding client device 110 a and/or location information of clientdevice 110 a at the time the subsequent request was transmitted, andupdate the representation of the data item to include the informationregarding the subsequent request.

In some other embodiments, when user 120 tries to access the same dataitem using client device 110 b (e.g., a personal computer as illustratedin FIG. 1), client device 110 b may transmit, to data management server100, a subsequent request to access the data item. In such cases, datamanagement server 100 may receive, from client device 110 b, thesubsequent request to access, with information regarding the subsequentrequest to access including device information regarding client device110 b and/or location information of client device 110 b at the time thesubsequent request was transmitted, and update the representation of thedata item to include the information regarding the subsequent request.

Although the example embodiments described with regard to FIG. 1illustrate that user 120 uses two client devices to access the dataitems provided by the online service provider, those skilled in the artwill readily appreciate that user 120 may use any number of clientdevices.

FIG. 2 schematically shows an illustrative example of a representation200 of data items that is displayed on client devices 110 a and/or 110b, arranged in accordance with at least some embodiments describedherein. Reference may be made to the embodiments depicted and describedwith reference to FIG. 1.

As depicted, representation 200 may include a displayed listing of dataitems that includes an indication 210 of whether each data item has beenpreviously accessed by one or more user accounts of user 120, senderinformation 220 regarding a source of each data item, title information230 including a title, header, or subject line of each data item, deviceinformation 240 regarding a device under the ownership and/or control ofuser 120 by which one or more data items may have been previouslyaccessed, and/or location information 250 regarding a location at whichone or more of the data items may have been previously accessed by theone or more user accounts. By way of example, but not limitation, thedata items listed in representation 200 may include electronic mails,posts in one or more SNS (social networking service), or news articlesposted by information sources to which user 120 has subscribed. Forinstance, when one or more of the data items are electronic mails,sender information 220 may indicate who sent the electronic mails, andtitle information 230 may list the subject line of the respectiveelectronic mails; when one or more of the data items are SNS posts,sender information 220 may indicate who wrote the SNS posts, and titleinformation 230 may list the subject line or at least introductory wordsof the respective SNS posts; and when one or more of the data items arenews articles, sender information 220 may indicate news organizationsthat published the respective news articles or journalists who wrote therespective news articles, and title information 230 may list at least aportion of the headline for each of the respective news articles.

In some embodiments, device information 240 may indicate by which clientdevice the one or more user accounts previously accessed each of therespective data items (e.g., a mobile device, a personal computer (PC),etc.). By way of example, but not limitation, device information 240 mayinclude at least one of a name of the client device, a type of theclient device, a screen size of the client device, a display resolutionof the client device, or information regarding a network to which theclient device is communicatively connected when each data item wasaccessed.

In some embodiments, location information 250 may indicate a location atwhich the one or more user accounts previously accessed each of therespective data items (e.g., at an address, at office, at home, in asubway, on a bus, etc.). By way of example, but not limitation, locationinformation 250 may include at least one of information regarding aregistered location that is specific to user 120 (e.g., office, home,etc.), a GPS (Global Positioning System) coordinate of the clientdevice, information regarding a cellular network to which the clientdevice is communicatively connected, information regarding a Wi-Fiaccess point to which the client device is communicatively connected, orinformation regarding communication between the client device and atleast one nearby beacon when each data item was accessed.

By providing the one or more user accounts with representation 200including device information 240 and location information 250 to bedisplayed on any device that user 120 may use, user 120 may keep trackof by which device he/she has accessed the respective data items and/orwhere he/she has accessed the respective data items.

FIG. 3 shows a schematic block diagram illustrating an examplearchitecture of data management server 100 for implementing a datamanagement scheme, arranged in accordance with at least some embodimentsdescribed herein. Reference may be made to the embodiments depicted anddescribed with reference to FIGS. 1-2.

As depicted, data management server 100 may include a receiver unit 310,a representation generation unit 320 and a user interface unit 330.Although illustrated as discrete components, various components may bedivided into additional components, combined into fewer components, oreliminated while being contemplated within the scope of the disclosedsubject matter. It will be understood by those skilled in the art thateach function and/or operation of the components may be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof.

Receiver unit 310 may be configured to receive, from client device 110 aor 110 b, a request to access a data item and information regarding therequest. The data item may be stored in and/or provided by a server of aservice provider (e.g., an electronic mail service provider, an SNSprovider, or an online content provider) that may host or otherwisecooperate with data management server 100.

In some embodiments, the information regarding the request may includeat least one of device information regarding client device 110 a or 110b or location information of client device 110 a or 110 b. By way ofexample, but not limitation, the device information regarding clientdevice 110 a or 110 b may include at least one of a name of clientdevice 110 a or 110 b, a type of client device 110 a or 110 b, a screensize of client device 110 a or 110 b, a display resolution of clientdevice 110 a or 110 b, or information regarding a network to whichclient device 110 a or 110 b was communicatively connected when receiverunit 310 received the request to access. Further, by way of example, butnot limitation, the location information of client device 110 a or 110 bmay include at least one of a registered location that is specific touser 120, a GPS (Global Positioning System) coordinate of client device110 a or 110 b, information regarding a cellular network to which clientdevice 110 a or 110 b is communicatively connected, informationregarding a Wi-Fi access point to which client device 110 a or 110 b iscommunicatively connected, or information regarding communicationbetween client device 110 a or 110 b and at least one nearby beacon whenreceiver unit 310 received the request to access.

Representation generation unit 320 may be configured to generate arepresentation of the data item to include the information regarding therequest to access that may be received by receiver unit 310. In someembodiments, when receiver unit 310 receives, from client device 110 aor 110 b, a subsequent request to access the same data item andinformation regarding the subsequent request to access, representationgeneration unit 320 may be further configured to update therepresentation of the data item to include the information regarding thesubsequent request to access.

User interface unit 330 may be configured to receive a request todisplay the representation of the data item from client device 110 a or110 b, and to provide client device 110 a or 110 b with therepresentation of the data item in response to the request to display.

FIG. 4 shows a schematic block diagram illustrating another examplearchitecture of data management server 100 for implementing a datamanagement scheme, arranged in accordance with at least some embodimentsdescribed herein. Reference may be made to the embodiments depicted anddescribed with reference to FIGS. 1-3.

As depicted, data management server 100 may include a data manager 400,an operating system 410 and a processor 420. Data manager 400 may be anapplication adapted to operate on operating system 410 such that thedata management scheme, as described herein, may be provided. Operatingsystem 410 may allow data manager 400 to manipulate processor 420 toimplement the data management scheme as described herein.

FIG. 5 shows a schematic block diagram illustrating an examplearchitecture of data manager 400 for implementing a data managementscheme, arranged in accordance with at least some embodiments describedherein. Reference may be made to the embodiments depicted and describedwith reference to FIGS. 1-4.

As depicted, data manager 400 may include an access request managementcomponent 510, a device information management component 520, a locationinformation management component 530, and a representation generationcomponent 540.

Access request management component 510 may be adapted to manage arequest, received from multiple client devices including client devices110 a and/or 110 b, to access a data item.

Device information management component 520 may be adapted to keep trackof an identification of a client device by which user 120 has requestedaccess to the data item. That is, device information managementcomponent 520 may detect device information regarding a client devicefrom which one or more requests to access the data item are received,and update the device information when access request managementcomponent 510 detects a subsequent request to access the data item.

Location information management component 530 may be adapted to keeptrack of a location from which user 120 has utilized a client device torequest access to the data item. That is, location informationmanagement component 530 may detect location information regarding alocation of user 120 when access request management component 510detects the request to access the data item, and update the locationinformation when access request management component 510 detects thesubsequent request to access the data item.

Representation generation component 540 may be adapted to generaterepresentation 200 of the data item to include the device informationand the location information respectively tracked by device informationmanagement component 520 and location information management component530. Representation generation component 540 may also be adapted toupdate the representation of the data item when access requestmanagement component 510 detects the subsequent request to access thedata item.

FIG. 6 shows an example flow diagram of a process 600 for a datamanagement server implementing a data management scheme, arranged inaccordance with at least some embodiments described herein.

Process 600 may be implemented in a data management server such as datamanagement server 100 including receiver unit 310, representationgeneration unit 320 and user interface unit 330. Process 600 may also beimplemented by computer programs or program modules that are adapted toprovide the data management scheme and hosted by a data managementserver, such as data manager 400 including access request managementcomponent 510, device information management component 520, locationinformation management component 530, and representation generationcomponent 540. Thus, reference may be made to the embodiments depictedand described with reference to FIGS. 1-5. Process 600 may include oneor more operations, actions, or functions as illustrated by one or moreblocks 610, 620, 630 and/or 640. Although illustrated as discreteblocks, various blocks may be divided into additional blocks, combinedinto fewer blocks, or eliminated, depending on the desiredimplementation. Processing may begin at block 610.

At block 610 (Receive Request to Access Data Item and InformationRegarding Request to Access), data management server 100 and/or datamanager 400 may receive, from client device 110 a or 110 b, a request toaccess a data item and information regarding the request to access. Theinformation regarding the request to access may include at least one ofdevice information regarding client device 110 a or 110 b or locationinformation of client device 110 a or 110 b. Processing may continuefrom block 610 to block 620.

At block 620 (Generate Representation of Data Item to IncludeInformation Regarding Request to Access), data management server 100and/or data manager 400 may generate a representation of the data itemto include the information regarding the request to access. Processingmay continue from block 620 to block 630.

At block 630 (Receive Subsequent Request to Access Data Item andInformation Regarding Subsequent Request to Access), data managementserver 100 and/or data manager 400 may receive, from client device 110 aor 110 b, a subsequent request to access the data item and informationregarding the subsequent request to access. The information regardingthe subsequent request to access may include at least one of deviceinformation associated with the subsequent request to access or locationinformation associated with the subsequent request to access. Processingmay continue from block 630 to block 640.

At block 640 (Update Representation of Data Item to Include InformationRegarding Subsequent Request to Access), data management server 100and/or data manager 400 may update the representation of the data itemto include the information regarding the subsequent request to access.Processing may continue from block 640 back to block 630 in someembodiments.

As such, data management server 100 and/or data manager 400 may providea user with the representation of the data item including the deviceinformation and/or the location information, thereby allowing the userto be aware by which device he/she accessed the data item and/or wherehe/she accessed the data item.

One skilled in the art will appreciate that, for this and otherprocesses and methods disclosed herein, the functions performed in theprocesses and methods may be implemented in differing order.Furthermore, the outlined steps and operations are only provided asexamples, and some of the steps and operations may be optional, combinedinto fewer steps and operations, or expanded into additional steps andoperations without detracting from the essence of the disclosedembodiments.

FIG. 7 illustrates an example computer program product 700 that may beutilized to implement a data management scheme, arranged in accordancewith at least some embodiments described herein.

As depicted, program product 700 may include a signal bearing medium702. Signal bearing medium 702 may include one or more instructions 704that, when executed by, for example, a processor of client device 110 aor 110 b, may provide the functionality described above with respect toFIGS. 1-6. By way of example, instructions 704 may include: one or moreinstructions for displaying a representation of a data item stored in adata storage; one or more instructions for displaying an indication ofwhether the data item has been accessed by a user account; or one ormore instructions for displaying information regarding a previous accessby the user account for the data item.

In some implementations, signal bearing medium 702 may encompass acomputer-readable medium 706, such as, but not limited to, a hard diskdrive, a CD, a DVD, a digital tape, memory, etc. In someimplementations, signal bearing medium 702 may encompass a recordablemedium 708, such as, but not limited to, memory, read/write (R/W) CDs,R/W DVDs, etc. In some implementations, signal bearing medium 702 mayencompass a communications medium 710, such as, but not limited to, adigital and/or an analog communication medium (e.g., a fiber opticcable, a waveguide, a wired communications link, a wirelesscommunication link, etc.). Thus, for example, program product 700 may beconveyed to one or more modules of client device 110 a or 110 b that mayinteract with data management server 100 and/or data manager 400 by anRF signal bearing medium 702, where the signal bearing medium 702 isconveyed by a wireless communications medium 710 (e.g., a wirelesscommunications medium conforming with the IEEE 802.11 standard).

FIG. 8 is a block diagram illustrating an example computing device 800that may be utilized to implement a data management scheme, arranged inaccordance with at least some embodiments described herein.

In a very basic configuration 802, computing device 800 typicallyincludes one or more processors 804 and a system memory 806. A memorybus 808 may be used for communicating between processor 804 and systemmemory 806.

Depending on the desired configuration, processor 804 may be of any typeincluding but not limited to a microprocessor (μP), a microcontroller(μC), a digital signal processor (DSP), or any combination thereof.Processor 804 may include one or more levels of caching, such as a levelone cache 810 and a level two cache 812, a processor core 814, andregisters 816. An example processor core 814 may include an arithmeticlogic unit (ALU), a floating point unit (FPU), a digital signalprocessing core (DSP Core), or any combination thereof. An examplememory controller 818 may also be used with processor 804, or in someimplementations memory controller 818 may be an internal part ofprocessor 804.

Depending on the desired configuration, system memory 806 may be of anytype including but not limited to volatile memory (such as RAM),nonvolatile memory (such as ROM, flash memory, etc.) or any combinationthereof. System memory 806 may include an operating system 820, one ormore applications 822, and program data 824.

Application 822 may include a data management algorithm 826 that may bearranged to perform the functions as described herein including theactions described with respect to the data management server 100architecture as shown in FIGS. 3-5 or including the actions describedwith respect to the flow charts shown in FIG. 6. Program data 824 mayinclude any data that may be useful for providing the data managementscheme as is described herein. In some examples, application 822 may bearranged to operate with program data 824 on an operating system 820such that the data management scheme as described herein may beprovided.

Computing device 800 may have additional features or functionality, andadditional interfaces to facilitate communications between basicconfiguration 802 and any required devices and interfaces. For example,a bus/interface controller 830 may be used to facilitate communicationsbetween basic configuration 802 and one or more data storage devices 832via a storage interface bus 834. Data storage devices 832 may beremovable storage devices 836, non-removable storage devices 838, or acombination thereof. Examples of removable storage and non-removablestorage devices include magnetic disk devices such as flexible diskdrives and hard-disk drives (HDD), optical disk drives such as compactdisk (CD) drives or digital versatile disk (DVD) drives, solid statedrives (SSD), and tape drives to name a few. Example computer storagemedia may include volatile and nonvolatile, removable and non-removablemedia implemented in any method or technology for storage ofinformation, such as computer readable instructions, data structures,program modules, or other data.

System memory 806, removable storage devices 836 and non-removablestorage devices 838 are examples of computer storage media. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich may be used to store the desired information and which may beaccessed by computing device 800. Any such computer storage media may bepart of computing device 800.

Computing device 800 may also include an interface bus 840 forfacilitating communication from various interface devices (e.g., outputdevices 842, peripheral interfaces 844, and communication devices 846)to basic configuration 802 via bus/interface controller 830. Exampleoutput devices 842 include a graphics processing unit 848 and an audioprocessing unit 850, which may be configured to communicate to variousexternal devices such as a display or speakers via one or more A/V ports852. Example peripheral interfaces 844 include a serial interfacecontroller 854 or a parallel interface controller 856, which may beconfigured to communicate with external devices such as input devices(e.g., keyboard, mouse, pen, voice input device, touch input device,etc.) or other peripheral devices (e.g., printer, scanner, etc.) via oneor more I/O ports 858. An example communication device 846 includes anetwork controller 860, which may be arranged to facilitatecommunications with one or more other computing devices 862 over anetwork communication link via one or more communication ports 864.

The network communication link may be one example of a communicationmedia. Communication media may typically be embodied by computerreadable instructions, data structures, program modules, or other datain a modulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. A “modulateddata signal” may be a signal that has one or more of its characteristicsset or changed in such a manner as to encode information in the signal.By way of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), microwave,infrared (IR) and other wireless media. The term computer readable mediaas used herein may include both storage media and communication media.

Computing device 800 may be implemented as a portion of a small-formfactor portable (or mobile) electronic device such as a cell phone, apersonal data assistant (PDA), a personal media player device, awireless web-watch device, a personal headset device, an applicationspecific device, or a hybrid device that include any of the abovefunctions. Computing device 800 may also be implemented as a personalcomputer including both laptop computer and non-laptop computerconfigurations.

The present disclosure is not to be limited in terms of the particularembodiments described in this application, which are intended asillustrations of various aspects. Many modifications and variations canbe made without departing from its spirit and scope, as will be apparentto those skilled in the art. Functionally equivalent methods andapparatuses within the scope of the disclosure, in addition to thoseenumerated herein, will be apparent to those skilled in the art from theforegoing descriptions. Such modifications and variations are intendedto fall within the scope of the appended claims. The present disclosureis to be limited only by the terms of the appended claims, along withthe full scope of equivalents to which such claims are entitled. It isto be understood that this disclosure is not limited to particularmethods, reagents, compounds, compositions or biological systems, whichcan, of course, vary. It is also to be understood that the terminologyused herein is for the purpose of describing particular embodimentsonly, and is not intended to be limiting.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more”); the same holds true for the use of definite articlesused to introduce claim recitations. In addition, even if a specificnumber of an introduced claim recitation is explicitly recited, thoseskilled in the art will recognize that such recitation should beinterpreted to mean at least the recited number (e.g., the barerecitation of “two recitations,” without other modifiers, means at leasttwo recitations, or two or more recitations). Furthermore, in thoseinstances where a convention analogous to “at least one of A, B, and C,etc.” is used, in general such a construction is intended in the senseone having skill in the art would understand the convention (e.g., “asystem having at least one of A, B, and C” would include but not belimited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc.). In those instances where a convention analogous to “atleast one of A, B, or C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, or C” wouldinclude but not be limited to systems that have A alone, B alone, Calone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). It will be further understood by those withinthe art that virtually any disjunctive word and/or phrase presenting twoor more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms. Forexample, the phrase “A or B” will be understood to include thepossibilities of “A” or “B” or “A and B.”

In addition, where features or aspects of the disclosure are describedin terms of Markush groups, those skilled in the art will recognize thatthe disclosure is also thereby described in terms of any individualmember or subgroup of members of the Markush group.

As will be understood by one skilled in the art, for any and allpurposes, such as in terms of providing a written description, allranges disclosed herein also encompass any and all possible subrangesand combinations of subranges thereof. Any listed range can be easilyrecognized as sufficiently describing and enabling the same range beingbroken down into at least equal halves, thirds, quarters, fifths,tenths, etc. As a non-limiting example, each range discussed herein canbe readily broken down into a lower third, middle third and upper third,etc. As will also be understood by one skilled in the art all languagesuch as “up to,” “at least,” and the like include the number recited andrefer to ranges which can be subsequently broken down into subranges asdiscussed above. Finally, as will be understood by one skilled in theart, a range includes each individual member. Thus, for example, a grouphaving 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, agroup having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells,and so forth.

From the foregoing, it will be appreciated that various embodiments ofthe present disclosure have been described herein for purposes ofillustration, and that various modifications may be made withoutdeparting from the scope and spirit of the present disclosure.Accordingly, the various embodiments disclosed herein are not intendedto be limiting, with the true scope and spirit being indicated by thefollowing claims.

1. A method, comprising: displaying, by a client device, arepresentation of a data item received from a server; transmitting, bythe client device, to the server, a request to access the data item andinformation regarding the request to access that includes at least oneof device information regarding the client device that has accessed thedata item or location information regarding a location at which theclient device has accessed data item, in response to a user input;updating, by the server, the representation of the data item to furtherinclude the information regarding the request to access; and displaying,by the client device, the updated representation of the data itemreceived from the server.
 2. (canceled)
 3. The method of claim 1,wherein the data item includes an electronic mail, a post in an SNS(social networking service), or a news article.
 4. A data managementserver, comprising: a receiver unit configured to receive, from a clientdevice, a request to access a data item and information regarding therequest to access that includes at least one of device informationregarding the client device or location information of the clientdevice; and a representation generation unit configured to generate arepresentation of the data item to include the received informationregarding the request to access.
 5. (canceled)
 6. The data managementserver of claim 4, wherein the device information regarding the clientdevice includes at least one of a name of the client device, a type ofthe client device, a screen size of the client device, a displayresolution of the client device, or information regarding a network towhich the client device was communicatively connected when the receiverunit received the request to access.
 7. The data management server ofclaim 4, wherein the location information of the client device includesat least one of information regarding a registered location that isspecific to a user of the client device, a GPS (Global PositioningSystem) coordinate of the client device, information regarding acellular network to which the client device is communicativelyconnected, information regarding a Wi-Fi access point to which theclient device is communicatively connected, or information regardingcommunication between the client device and at least one beacon when thereceiver unit received the request to access.
 8. The data managementserver of claim 4, wherein the receiver unit is further configured toreceive, from the client device, a subsequent request to access the dataitem and information regarding the subsequent request to access, andwherein the representation generation unit is further configured toupdate the representation of the data item to include the informationregarding the subsequent request to access.
 9. The data managementserver of claim 4, wherein the receiver unit is further configured toreceive, from another client device, a subsequent request to access thedata item and information regarding the subsequent request to access,and wherein the representation generation unit is further configured toupdate the representation of the data item to include the informationregarding the subsequent request to access.
 10. The data managementserver of claim 4, further comprising: a user interface unit configuredto receive a request to display the representation of the data item andto provide the representation of the data item.
 11. The data managementserver of claim 4, wherein the data item is an electronic mail.
 12. Thedata management server of claim 11, wherein the data management serveris hosted by an electronic mail service provider.
 13. The datamanagement server of claim 4, wherein the data item is a post on a pageof an SNS (social networking service).
 14. The data management server ofclaim 13, wherein the data management server is hosted by an SNSprovider.
 15. The data management server of claim 4, wherein the dataitem is a news article.
 16. The data management server of claim 15,wherein the data management server is hosted by an online contentprovider.
 17. A method performed under control of a data managementserver, comprising: receiving, from a client device, a request to accessa data item; receiving, from the client device, information regardingthe request to access that includes at least one of device informationregarding the client device or location information of the clientdevice; and generating a representation of the data item to include theinformation regarding the request to access.
 18. (canceled)
 19. Themethod of claim 17, wherein the device information regarding the clientdevice includes at least one of a name of the client device, a type ofthe client device, a screen size of the client device, a displayresolution of the client device, or information regarding a network towhich the client device is communicatively connected.
 20. The method ofclaim 17, wherein the location information of the client device includesat least one of information regarding a registered location that isspecific to a user of the client device, information regarding a GPS(Global Positioning System) coordinate of the client device, informationregarding a cellular network to which the client device iscommunicatively connected, information regarding a Wi-Fi access point towhich the client device is communicatively connected, or informationregarding communication between the client device and at least onebeacon.
 21. The method of claim 17, further comprising: receiving, fromthe client device, a subsequent request to access the data item;receiving, from the client device, information regarding the subsequentrequest to access; and updating the representation of the data item toinclude the information regarding the subsequent request to access. 22.The method of claim 17, further comprising: receiving, from anotherclient device, a subsequent request to access the data item; receiving,from the other client device, information regarding the subsequentrequest to access; and updating the representation of the data item toinclude the information regarding the subsequent request to access. 23.A computer-readable storage medium having stored thereoncomputer-executable instructions that, in response to execution, cause aprocessor to perform operations, comprising: displaying a representationof a data item stored in a data storage; displaying an indication ofwhether the data item has been accessed by a user account; anddisplaying information regarding a previous access by the user accountfor the data item, wherein the information regarding the previous accessincludes at least one of device information regarding a client deviceassociated with the user account that accessed the data item or locationinformation regarding a location at which the client device accessed thedata item.
 24. (canceled)
 25. The computer-readable storage medium ofclaim 23, wherein the device information regarding the client deviceincludes at least one of a name of the client device, a type of theclient device, a screen size of the client device, a display resolutionof the client device, or information regarding a network to which theclient device is communicatively connected when the data item wasaccessed.
 26. The computer-readable storage medium of claim 23, whereinthe location information includes at least one of information regardinga registered location that is specific to the user account, informationregarding a GPS (Global Positioning System) coordinate of the clientdevice, information regarding a cellular network to which the clientdevice is communicatively connected, information regarding a Wi-Fiaccess point to which the client device is communicatively connected, orinformation regarding communication between the client device and atleast one beacon when the data item was accessed.